在 Rust 中重新定义面向对象编程，意味着从僵化的类层次结构转向一种以 数据与行为分离为核心模型。虽然传统系统级语言依赖于复杂的对象树，但 Rust 通过使用 特质（traits） 和模块来实现面向对象设计的目标——封装与多态性，同时优先保障内存安全，且无需运行时开销。
1. 挑战层级结构
Rust 明确避免实现继承，以防止 脆弱基类 问题。相反，它更倾向于组合与 特质（Traits） 来定义跨不同类型共享的行为。这里的“对象”是数据（结构体）与操作这些数据的过程（impl 块）的组合，其正确性在编译时即被验证。
2. 并发与状态即类型
Rust 主要通过标准库（Send与Sync 特质）而非语言核心来处理并发。为了最大化安全性，采用 状态即类型算法 将不同的状态编码为不同类型。状态转换返回新的实例，从而将逻辑从运行时 if 语句转移到编译时要求。
main.py
TERMINALbash — 80x24
> Ready. Click "Run" to execute.
>
QUESTION 1
Why does Rust avoid implementation inheritance?
To prevent the 'fragile base class' problem where child classes break due to parent changes.
Because Rust does not support polymorphism.
To ensure all objects are stored on the stack.
Because traits are more memory-intensive than classes.
✅ Correct!
By favoring composition over inheritance, Rust avoids the complexity and tight coupling inherent in deep class hierarchies.❌ Incorrect
Rust supports polymorphism via traits; the avoidance of inheritance is a design choice to ensure maintainability.QUESTION 2
How does Rust define an 'object' according to the Gang of Four philosophy?
A runtime class pointer with a virtual table.
A combination of data (structs) and the procedures that operate on it (impl blocks).
A global variable accessible by any module.
An instance of a template class.
✅ Correct!
Rust uses structs for data and impl blocks for behavior, perfectly mirroring the GoF definition of an object.❌ Incorrect
While dynamic dispatch uses vtables, the core definition of an object in Rust is the pairing of data and methods.QUESTION 3
Where is concurrency logic primarily defined in Rust?
In the core language syntax.
Through mandatory thread models in the compiler.
Primarily through the standard library and external crates.
By the operating system only.
✅ Correct!
Rust's core is lightweight; traits like Send and Sync allow the standard library to handle concurrency safely.❌ Incorrect
Rust's core language doesn't dictate a threading model, allowing for zero-cost abstractions.QUESTION 4
What is the primary benefit of the State-as-Type algorithm?
It reduces the binary size of the application.
It allows for faster runtime execution via dynamic dispatch.
It turns invalid state transitions into compile-time errors.
It automatically generates documentation for states.
✅ Correct!
By making states distinct types, you cannot call a method meant for one state (e.g., 'approve') on a different state (e.g., 'Draft') at the compiler level.❌ Incorrect
The primary goal is safety and correctness, ensuring logic is validated before the program ever runs.QUESTION 5
In the 'encoding states as types' approach, how are state transitions handled?
By modifying a 'status' enum field in a single struct.
By consuming the current state type and returning a new state type.
By using a global state manager.
By casting pointers between different classes.
✅ Correct!
Transformation methods take ownership of 'self', ensuring the old state is invalidated and the new state is correctly initialized.❌ Incorrect
Modifying a field is the traditional OOP way; Rustaceans prefer type transformation for increased safety.Case Study: The Secure Document Workflow
Applying State-as-Type for Compile-Time Safety
You are designing a document system where a 'Draft' can be sent for review, becoming a 'PendingReview' object. You need to implement a 'reject' mechanism that safely returns a 'PendingReview' document back to a 'Draft' state.
Q
Add a reject method that changes the post’s state from PendingReview back to Draft.
Solution:
To implement the
This transition consumes the
To implement the
reject method within the State-as-Type context, we define it on the PendingReview struct to return a Draft: impl PendingReview {
pub fn reject(self) -> Draft {
Draft {
content: self.content,
}
}
}This transition consumes the
PendingReview instance (via self) and returns a new Draft instance, effectively moving the data back to its initial state type while invalidating the old state.Q
How does this implementation prevent a developer from editing a document that is currently in the PendingReview state?
Solution:
In this design, the
In this design, the
add_text method is only implemented for the Draft struct. Once the document is transformed into a PendingReview struct, the add_text method is no longer available on that instance. Any attempt to call it would result in a compile-time error, preventing unauthorized edits during the review process.